home *** CD-ROM | disk | FTP | other *** search
- Subject: FW_CODPart::WritePartInfo
- Sent: 7/15/96 1:19 PM
- Received: 7/15/96 1:31 PM
- From: Hutchings, Richard B. "Brad", brad@hutchings-software.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- So you all guessed the DR6 deadline was approaching, right?
-
- 2 comments on this method...
-
- (1) It should clear the storage unit first, or perhaps call
- FW_CPart::ClearPartStorage with that storage unit focused. I use the part
- info to hold data cached for each frame. One time the data got very big
- (about 200K - lots of copies of the same bitmap, I fixed that :-). Then, I
- deleted the objects which were in there, and the storage unit is still that
- large. I've even called ODStorageUnitView::DeleteValue - no luck. The file
- is still huge, and the only way to bring the file size down seems to be to
- remove the storage unit.
-
- (2) It doesn't look easy to subclass FW_CODPart. Considering that some
- protocol (offscreen canvases in particular) is not yet implemented, it
- would be useful to have macros that support that better. At least until the
- framework matures a little, or goes direct-to-SOM or whatever.
-
- Brad
-
- <mailto: "Brad Hutchings" brad@hutchings-software.com>
- <http://www.hutchings-software.com>
-
- Ask me about:
- Hutchings Software's Rapid-I(tm) Button
- Hutchings Software's Essential Strips(tm)
-